
<h1>F-engine is an Application Framework</h1>
<p>
    F-engine is a toolkit for people who build web application using PHP.  Its goal is to enable you to develop projects much faster than you could if you were writing code
    from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and
    logical structure to access these libraries. F-engine lets you creatively focus on your project by
    minimizing the amount of code needed for a given task.
</p>
<h2>F-engine is Free</h2>
<p>
    F-engine is licensed under an Apache/BSD-style open source license so you can use it however you please. 
    For more information please read the <a href="<?php echo site_url();?>userguide/license">license agreement</a>.
</p>
<!--<h2>F-engine Runs on PHP 4</h2>
<p>
    F-engine is written to be compatible with PHP 4. Although we would have loved to take advantage of the better object handling
    in PHP 5 since it would have simplified some things we had to find creative solutions for (looking your way, multiple inheritance),
    at the time of this writing PHP 5 is not in widespread use, which means we would be alienating most of our
    potential audience.  Major OS vendors like RedHat are moving slowly to support PHP 5, and they are unlikely to do so in the short term, so
    we felt that it did not serve the best interests of the PHP community to write F-engine in PHP 5.
</p>
<p>
    Note:  F-engine will run on PHP 5.  It simply does not take advantage of any native features that are only available in that version.
</p> -->
<h2>F-engine is Light Weight</h2>
<p>
    Truly light weight.  The core system requires only a few very small libraries. This is in stark contrast to many frameworks that require significantly more resources.
    Additional libraries are loaded dynamically upon request, based on your needs for a given process, so the base system
    is very lean and quite fast.
</p>
<h2>F-engine is Fast</h2>
<p>
    Really fast. We challenge you to find a framework that has better performance than F-engine.
</p>
<h2>F-engine Uses M-V-C</h2>
<p>
    F-engine uses the Model-View-Controller approach, which allows great separation between logic and presentation.
    This is particularly good for projects in which designers are working with your template files, as the code these file contain will be minimized. We describe MVC in more detail on its own page.
</p>
<h2>F-engine Generates Clean URLs</h2>
<p>
    The URLs generated by F-engine are clean and search-engine friendly.  Rather than using the standard "query string"
    approach to URLs that is synonymous with dynamic systems, F-engine uses a segment-based approach:
</p>
<code>
    example.com/
    <var>
        news
    </var>/
    <dfn>
        article
    </dfn>/
    <samp>
        345
    </samp>
</code>
<p>
    Note: By default the index.php file is included in the URL but it can be removed using a simple .htaccess file.
</p>
<h2>F-engine Packs a Punch</h2>
<p>
    F-engine comes with  full-range of libraries that enable the most commonly needed web development tasks, 
    like accessing a database, sending email, validating form data, maintaining sessions, manipulating images, working with XML-RPC data and 
    much more.
</p>
<h2>F-engine is Extensible</h2>
<p>
    The system can be easily extended through the use of plugins and helper libraries, or through class extensions or system hooks.
</p>
<h2>F-engine Does Not Require a Template Engine</h2>
<p>
    Although F-engine <em>does</em>
    come with a simple template parser that can be optionally used, it does not force you to use one.
    Template engines simply can not match the performance of native PHP, and the syntax that must be learned to use a template
    engine is usually only marginally easier than learning the basics of PHP.  Consider this block of PHP code:
</p>
<code>
    &lt;ul>
    <br/>
    <br/>
    &lt;?php foreach ($addressbook as $name):?>
    <br/>
    <br/>
    &lt;li>&lt;?=$name?>&lt;/li>
    <br/>
    <br/>
    &lt;?php endforeach; ?>
    <br/>
    <br/>
    &lt;/ul>
</code>
<p>
    Contrast this with the pseudo-code used by a template engine:
</p>
<code>
    &lt;ul>
    <br/>
    <br/>
    {foreach from=$addressbook item="name"}
    <br/>
    <br/>
    &lt;li>{$name}&lt;/li>
    <br/>
    <br/>
    {/foreach}
    <br/>
    <br/>
    &lt;/ul>
</code>
<p>
    Yes, the template engine example is a bit cleaner, but it comes at the price of performance, as the pseudo-code must be converted 
    back into PHP to run. Since one of our goals is <em>maximum performance</em>, we opted to not require the use of a template engine.
</p>
<h2>F-engine is Thoroughly Documented</h2>
<p>
    Programmers love to code and hate to write documentation.  We're no different, of course, but 
    since documentation is <strong>as important</strong>
    as the code itself,
    we are committed to doing it. Our source code is extremely clean and well commented as well.
</p>
